chore: maintenance mode — restrict Renovate to security updates only#883
Merged
andypitcher merged 2 commits intoMar 25, 2026
Merged
Conversation
Co-authored-by: andypitcher <12878731+andypitcher@users.noreply.github.com> Agent-Logs-Url: https://github.com/rancher/cis-operator/sessions/d64a7af9-2ec0-4c94-b4d1-8fe8a70f222a
Copilot
AI
changed the title
[WIP] Update README for security maintenance mode
chore: maintenance mode — restrict Renovate to security updates only
Mar 24, 2026
andypitcher
approved these changes
Mar 24, 2026
mitulshah-suse
approved these changes
Mar 25, 2026
andypitcher
deleted the
copilot/chore-maintenance-mode-restrict-renovate
branch
This was referenced Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repo is in security maintenance phase, superseded by rancher/compliance-operator. Two files updated to reflect that reality.
README.mdapi.securityscorecards.dev[!IMPORTANT]maintenance-phase callout after intro## Buildingand## Runningsections### How future release branches should be generated/removed, inlined)[rancher/security-scan]reference link to inline.github/renovate.jsonrancher-main#releaseopens all routine bumps — not appropriate for a maintenance-only repo. This PR adds an explicit disable rule formainso only CVE-driven alerts generate PRs. Release branches already enforce security-only via their upstream presets (rancher-2.10#release,rancher-2.11#release), no extra rule needed there.mainrelease/v1.4rancher-2.11#release(enforced upstream)release/v1.3rancher-2.10#release(enforced upstream)release/v1.2rancher-2.9#releasekept, no active targetingAfter merging, the following open Renovate PRs can be closed as out of scope:
PR #844 (x/crypto digest) should be reviewed individually — may carry a security fix.